|
Frame technology (FT) is a language-neutral (i.e., processes various languages) system that manufactures custom software〔Software is emphasized here; but given the appropriate frames, FT can assemble any kind of documents: technical and end-user manuals, UML models, test cases, legal contracts, bills-of-materials, etc.〕 from reusable, machine-adaptable building blocks, called frames. FT is used to reduce the time, effort, and errors involved in the design, construction, and evolution of large, complex software systems. Fundamental to FT is its ability to stop the proliferation〔S.Jarzabek and S.Li, "Eliminating Redundancies with a 'Composition and Adaptation' Meta-Programming Technique," Proc. European Software Eng. Conf./ACM/SIGSOFT Symp. Foundations of Software Engineering, (ESEC/FSE 03), ACM Press, 2003, pp. 237–246; received the ACM Distinguished Paper Award〕 of similar but subtly different components, an issue plaguing software engineering, for which programming language constructs (subroutines, classes, or templates/generics) or add-in techniques such as macros and generators failed to provide a practical, scalable solution. A number of implementations of FT exist. (Netron Fusion ) specializes in constructing business software and is proprietary. (XVCL ) is a general-purpose, open-source implementation of FT. Paul G. Bassett invented the first FT in order to automate the repetitive, error-prone editing involved in adapting (generated and hand-written) programs to changing requirements and contexts. A substantial literature now exists〔P.G.Bassett "Frame-Based Software Engineering", ''IEEE Software'', July 1987, pp. 9 -16〕〔( C.Holmes and A. Evens, "A Review of Frame Technology." Nov. 28 2003; )〕〔F.Sauer, "Metadata Driven Multi-Artifact Code Generation Using Frame Oriented Programming," ''Workshop on Generative Techniques in the context of Model Driven Architecture'' (Oopsla 02), 2002 ()〕〔H. Basit, D.C. Rajapakse, and S. Jarzabek, "Beyond Templates: A Study of Clones in the STL and some General Implications," Proc. Int'l Conf. Software Eng. (ICSE 05), ACM Press, 2005, pp. 451–459〕〔P.G. Bassett, ''Framing Software Reuse: Lessons from the Real World'', Prentice Hall, 1997.〕〔S. Jarzabek, ''Effective Software Maintenance and Evolution: A Reuse-based Approach'', Auerbach, 2007.〕〔P.G.Bassett, "The Case for Frame-Based Software Engineering," IEEE Software, July 2007, pp. 90–99〕〔P.G.Bassett, "Adaptive Components: Software Engineering's Ace in the Hole," Cutter Consortium's Agile Project Management, Vol.5 #5〕 that explains how FT can facilitate most aspects of software’s life-cycle, including domain modeling, requirements gathering, architecture and design, construction, testing, documentation, fine tuning and evolution. Independent comparisons of FT to alternative approaches〔I. Grossman and M. Mah, "Independent Research Study of Software Reuse", tech. report, QSM Associates, 1994〕 confirm that the time and resources needed to build and maintain complex systems can be substantially reduced. One reason: FT shields programmers from software’s inherent redundancies: FT has reproduced COTS object-libraries from equivalent XVCL frame libraries that are two-thirds smaller and simpler;〔〔 custom business applications are routinely specified and maintained by (Netron Fusion )SPC frames that are 5% – 15% of the size of their assembled source files.〔 ==Frames== Below are two informal descriptions, followed by a more precise definition and explanation. :#A frame is an adaptable component on an automated software assembly line. Imagine an auto factory where, instead of having specific bumpers, fenders, and other parts to suit the specifics of each car model, we have just one generic bumper, one generic fender, and so on. Now imagine that these generic parts could be cloned and shaped to fit each car model as it came down the line. Such a fantasy would revolutionize manufacturing; and while impossible for physical parts, this is what frames do for software (and information in general). :#A frame is a recipe for "cooking up" a (program) text. Its instructions say how to blend its ingredients – chunks of frame-text within itself – with the ingredients from other frames. The “chef” is a frame processor that carries out the instructions, i.e. the frame commands, which alter (add, modify, delete) ingredients as necessary, to suit the main recipe. Formally, a frame is a procedural macro consisting of frame-text – zero or more lines of ordinary (program) text and frame commands (that are carried out by FT’s frame processor as it manufactures custom programs). Each frame is both a generic component in a hierarchy of nested subassemblies, and a procedure for integrating itself with its subassembly frames (a recursive process that resolves integration conflicts in favor of higher level subassemblies). The outputs are custom documents, typically compilable source modules. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Frame technology (software engineering)」の詳細全文を読む スポンサード リンク
|